Case Model Properties Interface |
|
The Properties - Case Model pane helps in viewing and setting the properties of a Case model.
Table 1. Fields on the Properties - Case Model Pane
Tab | Field | Description | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
General | Name | Name of the current Case model. This is a mandatory field. | ||||||||||||||
Description | Provide a description for the Case model. | |||||||||||||||
Root State Name | All the follow-up activities defined in the model, that are not associated to any specific user-defined State, will be considered to be part of this state. This is an editable field and if required, you can modify the default name provided. The state name provided here can be selected by the Inbox users to list the follow-up activities which are not associated to any specific user-defined State. | |||||||||||||||
Priority | When multiple Case models are executed, the Case instances corresponding to these Case models are created. The priority displays the various levels of the Case model, which assumes importance in the run-time. Using the Priority list, you can select the priority level High, Medium or Low and provide the priority of execution. Note: If the priority is not set, the Case instances will be executed in FIFO (First-In, First-Out) order. During execution, the Case model with High priority will take precedence over the Case models that are set to lower priority levels. |
|||||||||||||||
Case Overview Form | A Case overview form is an User Interface (UI) that allows you to view the data related to a Case. In the UI, the information related to the Case data is displayed in the Case Inbox and CIM (Case Instance Monitoring). When a Case overview form is configured for any Case model, all the users working on that Case model will be able to access the Case overview form. Select the required overview form to attach to the Case model. Also, you can add a New User Interface or External User Interface or add an existing one from the Select a Case Overview Form window. In the Case overview form, use the SOAP API GetCaseData to access the data associated to a Case instance and populate the controls in the Case overview form. |
|||||||||||||||
Applicability Service | Often, the case workers or knowledge workers need to take decisions to select the most applicable sub-set from next set of follow-up activities, based on the context and data available for a Case. In such a scenario, it becomes necessary for a case worker to consider all the possible options and exceptions available for executing a task. The Applicability Service is a feature that helps a case worker to accomplish tasks easily, while considering all the possible options and exceptions, by implementing the required business logic on a Web service. When the Applicability Service feature is selected for the state, it becomes applicable for all the activities within the state. When the activities within the state are executed, based on the work option or exception, Applicability Service is triggered. Refer to Using the Applicability Service in a Case Model for more information on configuration and related usage.
|
|||||||||||||||
Data | Use XML Schema Fragment | A data model gives the structure of the information in the Case model. Select the required XML schema fragment for the Case to add a data model to the Case model. By using CreateCase SOAP API, you can trigger the Case model and pass the instance of the data model. |
||||||||||||||
Case Identifiers |
|
|||||||||||||||
Duration | Business Calendar | Business Calendar allows you to associate the timely business activities with the Case model. Select the required Business Calendar from the available list and attach to the Case model. If you wish to continue with the default calendar, that is 24*7, do not provide any changes. | ||||||||||||||
Duration Type | ||||||||||||||||
Escalate to | Escalate to allows you to send notifications to the concerned member working on the Case so as to ensure that the Case will be completed at the earliest possible time. Select the member to whom you wish to send the notification from the list mentioned below.
Note: The escalation feature in Case model notifies the receiver. It will not support the re-assignment of a task. |
|||||||||||||||
User | To indicate which case worker must work on the Case, select a case worker. This helps to allocate appropriate case workers to work on the Case. Note: This option is enabled only if User defined by case variable is selected in the Escalate to list. |
|||||||||||||||
Case Variables |
Case Variables | A Case variable is used as a parameter in a Case model. It has a type and a default value. A Case model can have zero or more variables and collectively define exactly, which parts of the model can be changed. You can create your own Case variables on any Case model by using the Case Variables tab on the Case model properties page. Case variables help case workers to regulate Case execution behavior at run time, by delaying the specification of certain Case element values, till the instance is actually executed. A lot of decisions are made during design time by the case worker, for example; activities, norm times, business calendars and so on. However, some properties have to be decided by the case worker during run time. To facilitate this process, custom Case variables can be defined with default values by the Case designer. They can be set by the case worker only while creating a Case or updating a Case variable Web services during the run time of the Business Process Model.
|
||||||||||||||
Work Assignment | Assignee Type | Based on your business requirements, you may have a single case worker, multiple case workers, or teams working on the Case. Therefore, it is important to select an assignee type to clearly indicate who must work on the current Case. Click
|
||||||||||||||
Work Distribution | Work distribution is a custom algorithm, which you must define to indicate how the work must be distributed among the case workers. Select one of the following work distribution algorithm:
|
|||||||||||||||
Events | Event Name | Name of the event that you have created. At times, you may want to define your own event types that are specific for the Case model. Once you create the event types, you can use them at several places. You can use an event to describe what can happen when certain situations like receiving a document, creation of a Case, completion of an activity occur. On an activity, you can also specify the event it can raise. You can use an event to trigger a transition between states. For example, Event Name: OrderApproval. Click ![]() |
||||||||||||||
Description | A meaningful description of the event created. | |||||||||||||||
Attachments Note: The access control list (ACL) or permissions (Read, Write, Delete) defined in the Case model property sheet are applicable to all tasks in the respective Case model. |
Label Name | Name of the attachment definition. The label name associated with a Document Received Event must not contain the space ( ) character. | ||||||||||||||
Supported Document Types | Case models invariably have the need to use applicable or supported Case documents. The Supported Document Types displays a list of all the existing document types that new attachment definition supports. Click ![]() Note: If a required document type is not available in the list, select Any file type. |
|||||||||||||||
Read | Select the check box to enable the case worker to download the attached document in the Inbox. | |||||||||||||||
Write | Select the check box to enable the case worker to download the attachment, modify it, or add a new attachment to the task in the Inbox. | |||||||||||||||
Delete | Select the check box to enable the case worker to view the attachment in the Inbox, modify the contents in the attachment, add another attachment, or delete the attachment too. | |||||||||||||||
Annotation | Annotation | Provide any additional notes or comments on the Case model. |